home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
IRIX Installation Tools & Overlays 2004 February
/
SGI IRIX Installation Tools & Overlays 2004 February - Disc 1.iso
/
relnotes
/
nfs
/
ch5.z
/
ch5
Wrap
Text File
|
2004-01-09
|
4KB
|
133 lines
- 1 -
5. _K_n_o_w_n__P_r_o_b_l_e_m_s__a_n_d__W_o_r_k_a_r_o_u_n_d_s
This chapter describes the known problems in release 6.5 of
NFS.
+o NFS UDP traffic currently takes precedence over NFS TCP
traffic. As a result, sites using a mix of UDP & TCP
for NFS access might perceive slow performance of NFS
over TCP. (Bug #571214)
+o There is a known cachefs performance problem. (Bug
#550268)
+o Ejecting a CDROM can result in a stale NFS file handle.
(Bug #567372) The workaround is to unmount the CRDOM
before ejecting the CD.
+o The automounter cannot unmount a file system if its
file handle is stale. The workaround is to unmount the
file system using umount(1M) then send the automount
process a SIGHUP, so that it will update its tables.
Below is a list of known problems or potential problem areas
with the diskless product.
+o A diskless server must be assigned an NIS domain name,
even when the server is not using NIS. This means that
_n_f_s._s_w._n_i_s must be installed on a diskless server. (If
the domain name appears in the /_v_a_r/_y_p/_y_p_d_o_m_a_i_n file,
the network startup script sets the domain name when
the server reboots, even if NIS is not enabled on the
server.)
+o Occasionally, _s_h_a_r_e__i_n_s_t or _c_l_i_e_n_t__i_n_s_t exit instead of
resuming after _i_n_s_t exits. If this happens, correct
the problem in this way:
1. Start the _s_h_a_r_e__i_n_s_t or _c_l_i_e_n_t__i_n_s_t script again.
2. Immediately after the _i_n_s_t menu is displayed,
type quit and wait for the exit sequence to
complete.
+o The /_u_s_r/_l_o_c_a_l directory has not changed. This implies
that clients cannot write their own binaries to this
directory since /_u_s_r is read-only. System
administrators should determine how they want to handle
the notion of /_u_s_r/_l_o_c_a_l. To maintain the typical
model where each host gets its own /_u_s_r/_l_o_c_a_l, make
/_u_s_r/_l_o_c_a_l a symlink to ../_v_a_r/_l_o_c_a_l. Leaving shareable
objects under /_u_s_r/_l_o_c_a_l will allow them to be seen by
- 2 -
all diskless clients using a particular share tree.
+o Likewise, /_u_s_r/_p_e_o_p_l_e is on a read-only partition by
default. If home directories can be tied to specific
machines, the /_u_s_r/_p_e_o_p_l_e directory can be replaced
with a symlink to /_h_o_m_e. However, if home directories
need to be location transparent, then /_u_s_r/_p_e_o_p_l_e could
be a large exported partition on the diskless server
that each client mounts. Alternatively, home directory
symlinks can point to automounted directories on the
diskless server. In order to use the standard system
tools to create new users with home directories not in
/usr/people, the file /usr/lib/X11/app-defaults/Cpeople
needs to be modified. The line
****iiiinnnnttttllll....llllaaaabbbbeeeellll____HHHHOOOOMMMMEEEEDDDDIIIIRRRR:::: ////uuuussssrrrr////ppppeeeeoooopppplllleeee////
can be replaced with something like
****iiiinnnnttttllll....llllaaaabbbbeeeellll____HHHHOOOOMMMMEEEEDDDDIIIIRRRR:::: ////hhhhoooommmmeeee////
The guest home directory should move as needed.